-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move calendar initialization to server startup #5037
Move calendar initialization to server startup #5037
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
engine/time/src/main/java/io/deephaven/time/calendar/BusinessCalendarXMLParser.java
Outdated
Show resolved
Hide resolved
68859ac
to
bc49c3e
Compare
engine/time/src/test/java/io/deephaven/time/calendar/CalendarInit.java
Outdated
Show resolved
Hide resolved
Integrations/src/test/java/io/deephaven/integrations/python/CalendarsHelper.java
Outdated
Show resolved
Hide resolved
Plot/src/test/java/io/deephaven/plot/axistransformations/CalendarInit.java
Outdated
Show resolved
Hide resolved
engine/time/src/test/java/io/deephaven/time/calendar/CalendarInit.java
Outdated
Show resolved
Hide resolved
import io.deephaven.time.calendar.BusinessCalendar; | ||
import io.deephaven.time.calendar.Calendars; | ||
|
||
public final class CalendarsHelper { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test configuration for calendars feels like it is spread all over the place. CalendarsHelper
and two different CalendarInit
do roughly the same thing in different ways, including the opaque, undocumented noop()
method. Is there any reason that all of this logic shouldn't be consolidated into a single Calendars.addCalendarsFromConfiguration()
method?
No description provided.